Skip to main content
Version: 7.9

Viewing Automation Execution Results

To view Runbook task results, navigate to the active Worksheet. The Start and End tasks are components of the automation model that indicate the start/end of a sequence. If there is no End task result listed or ActionTasks are executed after the End task, the automation to be checked for errors.

The execution status (whether opened, completed, or aborted) of any process or task in a Runbook can be checked with the Request History main menu. Execution results are typically displayed on the Runbook wiki page for users who might not have access to Worksheets. The {result} markups will show Worksheet-like results on the wiki page, while the {detail} markups will show task detail output.

Viewing the immediate automation results during Runbook development helps to spot potential problems with the process. There are several types of problems:

  • Automation does not start execution.
  • Actual automation results differ from expected results (logical error).
  • Automation does not terminate as expected.
  • The automation might timeout (default timeout threshold is 10 minutes, configurable in the Start task).
  • The process ends without completing all expected ActionTasks.

Use the automation results in conjunction with appropriate log files to troubleshoot automation errors:

  • Add trace or debug information to ActionTasks.
  • Replace ActionTasks in the automation model with a no-op (no operation) task, specifically, the "noop" wait task with 0-seconds interval.
  • Or consider a generic message task ("comment") for feedback.
  • Verify all parameters to assure values are passed.
  • Create a task that displays the state of all variables.
  • Also, check RSControl/RSRemote logs to verify where values change.
  • Check the operational status of Resolve Actions Pro components and communications.

Checking Runbook Execution Status​

Each Runbook execution creates a Process Request which consists of multiple Task Requests. Process and Task Requests are mainly used for auditing and troubleshooting purposes. Older Process and Task Requests can be archived to maintain active tables at manageable sizes.

To view the execution status of an automation process, go to the Request History menu and select to view either Open or Completed Process Requests. The Aborted Processes can also be seen. Any of the Process Request lists display the most recent Runbooks filtered by corresponding execution status.

note

Only OPEN process requests can be aborted. Process in status COMPLETED cannot be aborted.

The System Information icon  opens execution duration, timestamp, process user, and other detailed information. То see process details, click the More Information icon or the Process Request number in the process list. Clicking the corresponding WS number under the Worksheet column for a process, accesses the process' Worksheet and displays the Results tab screen.

Searching Runbook Execution Results​

If you do not see the process request you are looking for on the first page, then you can perform a quick search in the Search input field by :

  • Process request number, using the following expression:  Process Request equals "PROC-number"
  • Process request Status, using the following expression: Status equals Completed/ Aborted/  Open
  • Process request creator, using the following expression: Created By equals "user"
  • Worksheet number, using the following expression: Worksheet equals "WS-number"

If a complex search criterion, that combines several conditions, needs to be applied, use the Advanced search options. It allows you to search by a number of criteria, including Process request, Status, Worksheet, Runbook, Duration, Created On, Created By, Updated On, Updated By.